Release 10.1A: OpenEdge Deployment:
WebClient Applications

Prompting the end user for authentication information

Instead of embedding authentication information in a server URL, you can have WebClient prompt the end user for them when they are needed.

How you do this depends on whether the server is an application-configuration-file server from which the application configuration file is downloaded, or a codebase server from which application components are downloaded. To prompt end users:

For an application-configuration–file server, go to the Application Assembler’s Configuration File Locator Definition window. In the Authentication Information group box, fill in the End-User Description field and check the Prompt for ID/Password (Unless Cached) box.

Figure 5–2 shows the WebClient Application Assembler’s Configuration File Locator Definition window.



Figure 5–2: Enabling WebClient to prompt for configuration file server authentication information
Note: WebClient uses this information only if the end user starts an already-installed WebClient application by using a shortcut. For more information on starting an already-installed application with a shortcut, see Chapter 7, " Deploying an Application."

Figure 5–3 shows the subsequent authentication prompt displayed to the end user.



Figure 5–3: Configuration file server authentication prompt
For a codebase server, go to the Application Assembler’s Codebase Locator Definition window. In the Authentication Information group box, fill in the End-User Description field. Then, check the Prompt for ID/Password (Unless Cached) box. Finally, if the codebase server is an AppServer, check the Prompt for AppServerID/Password/Info String (Unless Cached) box.

Figure 5–4 shows the Application Assembler’s Codebase Locator Definition window.



Figure 5–4: Enabling WebClient to prompt for codebase server authentication information

Figure 5–5 shows the subsequent authentication dialog box displayed to the end user.



Figure 5–5: Codebase server authentication prompt